From: Jim Blandy Date: Tue, 16 Mar 1993 18:35:04 +0000 (+0000) Subject: * bytecomp.el (byte-compile-from-buffer): Put buffer containing X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1^2~5^2~96844 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=1db01b1ab5e321cce8de06006766ce1b8b7a17e7;p=emacs.git * bytecomp.el (byte-compile-from-buffer): Put buffer containing compiled code in binary overwrite mode. --- diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index 331d51c779f..eb2b1a22c31 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -1256,7 +1256,15 @@ With argument, insert value in current buffer after the form." (set-buffer (get-buffer-create " *Compiler Output*"))) (erase-buffer) ;; (emacs-lisp-mode) - (setq case-fold-search nil)) + (setq case-fold-search nil) + + ;; This is a kludge. Some operating systems (OS/2) need to + ;; write files containing binary information specially. + ;; Under most circumstances, such files will be in binary + ;; overwrite mode, so those OS's use that flag to guess how + ;; they should write their data. Advise them that .elc files + ;; need to be written carefully. + (setq overwrite-mode 'overwrite-mode-binary)) (displaying-byte-compile-warnings (save-excursion (set-buffer inbuffer)